PU 500: Improved synchronisation for Arbodienst Integration (Dutch legislation)
Note: This document is only applicable to participants of the controlled
release phase for this solution.
Previously, the synchronisation of employee data from Exact Synergy to Arbodienst was done manually.
From this
product update onwards, the synchronisation is done automatically and is triggered
when changing certain employee data.
This change is only applicable when the following two options are enabled:
- The option All
active employees is selected at Synchronise
employee data to Arbodienst in the Arbodienst section of the
division card (accessible through Modules > HRM > Setup > Organisation >
Divisions), and
- The option Export
file or Web service is selected at Synchronise: Method in the
Arbodienst
section of the HRM settings (accessible through Modules > HRM
> Setup > General > Settings).
Scenario 1 – Change the employee type or status
This
scenario covers the following:
- Create a new employee.
- Change the status of an employee to Active.
- Change the type of applicant to Employee or Temporary.
- Change the type of student or contractor to Employee
or Temporary.
Keep in mind: When creating a new employee and when changing an
applicant to an employee or temporary, a new contract is generated
automatically, but you must manually fill the sequence number in the created contract
for the information to be synchronised.
You can do this using the Contract sequence number field in the contract by clicking Contract under the Monitor
section of the person's card.
Scenario 2 – Change other employee fields
This
scenario covers the following:
- The employee has no absence reports linked. In this case, only the employee XML file is generated.
- The employee has absence reports linked. In this case, the synchronisation is not affected by the Synchronise employee data to Arbodienst setting in the division card.
The table
below displays which XML file is generated, and which fields trigger the
synchronisation.
|
Fields
in person card
|
XML
file to be generated
|
Employee
without absence report linked
|
Employee
with absence report(s) linked
|
1
|
First name
|
Employee
|
Absence report
|
2
|
Last name
|
Employee
|
Absence report |
3
|
Initials
|
Employee
|
Absence report |
4
|
Middle name
|
Employee
|
Absence report |
5
|
Name in official communication
|
Employee
|
Absence report |
6
|
Gender
|
Employee
|
Absence report |
7
|
Social security no.
|
N/A, no XML file generated
|
Absence report |
8
|
Date of birth
|
Employee
|
Absence report |
9
|
Date of death
|
N/A, no XML file generated
|
Absence report |
10
|
Contract end date
|
Employee
|
Absence report |
11
|
Job title
|
Employee
|
Absence report |
12
|
Zip code
|
Employee
|
Absence report |
13
|
City
|
Employee
|
Absence report |
14
|
Address 1
|
Employee
|
Absence report |
15
|
Number (Address)
|
Employee
|
Absence report |
16
|
Phone (Personal)
|
Employee
|
Absence report |
17
|
Mobile (Personal)
|
N/A, no XML file generated
|
Absence report |
18
|
Phone (Work)
|
N/A, no XML file generated
|
Absence report |
19
|
Mobile (Work)
|
N/A, no XML file generated
|
Absence report |
20
|
E-mail (Personal)
|
N/A, no XML file generated
|
Absence report |
21
|
E-mail (Work)
|
N/A, no XML file generated
|
Absence report |
22
|
FTE
|
Employee
|
Employee*
|
|
Fields
in contract card
|
XML
file to be generated
|
Employee
without absence report linked
|
Employee
with absence report(s) linked
|
1
|
Contractual hours per week
|
Employee
|
Absence report |
2
|
Employment type
|
Employee
|
Absence report |
3
|
Reason end of employment (Arbodienst)
|
Employee
|
Absence report |
4
|
Start date
|
Employee
|
Absence report |
5
|
Contract sequence number
|
Employee
|
Absence report |
* When the
FTE is modified, the employee XML file is generated because the FTE information
is not available in the absence report XML file.
Main Category: |
Attachments & notes |
Document Type: |
Release notes detail |
Category: |
|
Security level: |
All - 0 |
Sub category: |
|
Document ID: |
30.478.979 |
Assortment: |
Exact Synergy Enterprise
|
Date: |
19-05-2022 |
Release: |
|
Attachment: |
|
Disclaimer |